openinte.htm

Open Integration: Expandable Solution Protects Your Investment

Handles Custom Objects | PowerBuilder & Visual Basic Testing | Full 32-Bit Support

QualityWorks has an open QA architecture that protects and leverages your QA investment. Its QA Partner Extension Kit lets you easily handle your difficult-to-test custom objects. What's more, it's enabled Segue to build links to the rapid application development environments -- PowerBuilder, SQLWindows, Visual Basic, XVT and others that you have invested so heavily in and work with every day.

QA Partner Extension Kit -- The Extension Kit option enables you to design and write your own external QA Partner Agent functions in C or C++ to interact with your custom objects and controls functions that your test scripts can call and use in exactly the same way they do standard Agent functions.
Real-World PowerBuilder Testing -- Get full 16- and 32-bit PowerBuilder support for testing your Windows applications. QualityWorks for PowerBuilder recognizes all Data Windows and DataWindow objects, down to each row and column. It can recognize and manipulate DataWindow objects like Check Boxes and Drop Down Data Windows and Data Window styles, like Tabular and Grid. And with true object-level recording, your scripts will be able to survive changes to your PowerBuilder applications. Continuous script rewriting and cascading errors are things of the past.
Real-World Visual Basic Testing -- Get full 16- and 32-bit Visual Basic support for testing your Windows applications. Now QualityWorks lets you automatically define and directly manipulate and test any ActiveX property in the Visual Basic 4 environment. Capture ActiveX definitions and record robust test scripts to drive your Visual Basic 4 applications and custom controls with a simple point-and-click. With GO! for Visual Basic, there's absolutely no coding required, property verification is completely automatic and you'll be able to test your ActiveXs with a high level of control comparable to the control you currently have over native objects. And if you're migrating your applications from Visual Basic 3 to Visual Basic 4, you can use your Visual Basic3 QA Partner scripts to directly test your Visual Basic 4 applications.

Send me full Open Integration product information.

Home